Thank you very much for the code, but I'm afraid that there is still one step to get it work.

I set options(pkgdown.internet = F) in my ~/.Rprofile, then

> pkgdown::build_home()
── Building home ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Reading 'news.md'
Writing 'index.html'
── Previewing site ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
> pkgdown::build_site()
══ Building pkgdown site ═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════
Reading from: '/media/computer/work/R/hgnc'
Writing to:   '/media/computer/work/R/hgnc/docs'
── Initialising site ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Writing 'sitemap.xml'
● Edit '_pkgdown.yml'
── Building home ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Reading 'news.md'
Error in curl::curl_fetch_memory(url, handle = handle) : 
  Could not resolve host: cloud.r-project.org
Calls: withCallingHandlers ... request_fetch.write_memory -> <Anonymous> -> .handleSimpleError -> h
Execution halted
Error in curl::curl_fetch_memory(url, handle = handle) : 
  Could not resolve host: cloud.r-project.org

I found that build_site() use new_process = TRUE by default.

In this scenario, I think it's quite intuitive to enable .Rprofile in the new process or at least add option to let the user explicitly specify it.

Otherwise, user have to run pkgdown::build_site(new_process = F) (I don't think it's a good idea to have to run pkgdown in a dirty process in order to get pkgdown.internet working)

I think we need to add user_profile = TRUE to the callr::r() call.

But then you have to set the option via .Rprofile.

Yeah, I think it's the natural way.

I think it would be better to set the option explicitly in the new process

How can you achieve that? build_site(process_setup = function() {options(pkgdown.internet = F)})? I think the syntax is ugly.

Instead .Rprofile is the natural way to run set up code before a R process begins. we can use build_site(use_Rprofile = TRUE).

The only drawback is when user want to run some code in build_site(new_process = T), but not in build_site(new_process = F). However, in normal case, I think this need is rare.

pkgdown would do it for you.

Writing to .Rprofile is not a good solution.

If the user develops multiple packages, specify that in every build_site() is rather tedious. .Rprofile is a much better choice.

Another way is to set it in _pkgdown.yml, like what I proposed in #762 (comment)

Maybe we can have something like

setup:
  code: options(pkgdown.internet = F)

or

setup:
  options:
    pkgdown.internet: F

👍 For me the builds now run through with:

options(pkgdown.internet = FALSE)
pkgdown::buil_site(new_process = FALSE)

⚡ But there are more problems ahead. Since internet is no option looking at the docs in a browser will result in several files the browser cannot obtain:

• jquery-3.1.0.min.js
• bootstrap.min.css
• bootstrap.min.js
• font-awesome.min.css
• clipboard.min.js
• sticky-kit.js
• Math.Jax.js?config=Tex-AMS-MML_HTMLorMML

@petermeissner I know this way, the down point is that we have to run pkgdown in a dirty session.

I think we might have gone so far.

What I'm talking about originally is to disable internet for building the documentation, not for viewing the documentation.

Maybe we need separate option for these two senarios.

@jayhesselberth 56f3a65#r30192460

https://cran.r-project.org/package= may be better than https://cloud.r-project.org/package= ?